Make snowpark optional for snowflake provider and disable it for Pyth…#53489
Merged
potiuk merged 1 commit intoapache:mainfrom Jul 18, 2025
Merged
Make snowpark optional for snowflake provider and disable it for Pyth…#53489potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
…on 3.13 It seems that despite explicit "Requires-Python <3.13" in snowpark client library, uv installs it on Python 3.13. This is tracked here astral-sh/uv#14711 However, it also means that we have to exclude snowpark fro being installed on Python 3.13 explicitly in provider requirements and conditionally skip the tests for it. We also need to bump version of the provider in package configuration and provider.yaml, because then snowflake provider used to be installed in CI will use the provider built locally rather than the one from PyPI that does not have such exclusion yet.
Member
Author
|
Applied "all versions" label to test running tests on Python 3.13 |
gopidesupavan
approved these changes
Jul 18, 2025
eladkal
reviewed
Jul 18, 2025
karenbraganz
pushed a commit
to karenbraganz/airflow
that referenced
this pull request
Jul 18, 2025
…on 3.13 (apache#53489) It seems that despite explicit "Requires-Python <3.13" in snowpark client library, uv installs it on Python 3.13. This is tracked here astral-sh/uv#14711 However, it also means that we have to exclude snowpark fro being installed on Python 3.13 explicitly in provider requirements and conditionally skip the tests for it. We also need to bump version of the provider in package configuration and provider.yaml, because then snowflake provider used to be installed in CI will use the provider built locally rather than the one from PyPI that does not have such exclusion yet.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…on 3.13
It seems that despite explicit "Requires-Python <3.13" in snowpark client library, uv installs it on Python 3.13.
This is tracked here astral-sh/uv#14711
However, it also means that we have to exclude snowpark fro being installed on Python 3.13 explicitly in provider requirements and conditionally skip the tests for it.
We also need to bump version of the provider in package configuration and provider.yaml, because then snowflake provider used to be installed in CI will use the provider built locally rather than the one from PyPI that does not have such exclusion yet.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.